Universal tag for page analytics and campaign creation

ABSTRACT

A system for creating and using a universal tag to gather consumer data from a website for the purposes of targeted advertising is provided. The universal tag system has two main subsystems. The first subsystem is a configuration system that is used to define the consumer data to be collected from the website and to define taxonomy and transformation rules to be applied to the collected consumer data. The second subsystem is a runtime system that runs a universal tag client-side script, which is triggered when a consumer lands on a webpage of the website, for collecting the defined consumer data. The runtime system then applies the transformation rules to the collected data and updates a user profile corresponding to the consumer with the transformed data. As well, the runtime system applies the taxonomy rules to the collected data and categorizes the consumer for the purposes of subsequent targeted advertising.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional patent applicationSer. No. 61/801,001, filed Mar. 22, 2013, which application isincorporated herein in its entirety by this reference thereto.

BACKGROUND OF THE INVENTION Technical Field

This invention relates generally to digital advertising. Moreparticularly, this invention relates to a tool for creating and using auniversal tag to gather consumer data for the purposes of digitaladvertising.

Description of the Related Art

The Internet has become a primary source for providing media andinformation. For example, it is believed that more news articles areread online than in print. Videos and television shows are increasinglyviewed through online applications, such as by the companies, Hulu,Netflix, and YouTube. Many of these online media companies earn revenueby allowing advertisers to advertise on their websites. The need ofcompanies with online presence to generate revenue by sellingadvertising space on their websites is met with the need of advertisersto reach consumers via online advertising. This mutual need has led tothe development of a niche industry, online display advertising. Thus,from the advertisers' point of view, it is an important aspect of theirbusiness to optimize their digital advertising potential on theInternet.

Although the system of advertising in print media has been wellestablished for centuries, the rules for online advertising are stillevolving. As users demand instant access to entertainment their patiencefor advertisements rapidly dwindles. For example, if a user is forced toview a pre-roll advertisement before a video is displayed, the user maysimply click on another window or walk away from the display screenuntill the advertisement is gone. Thus, such user is not watching theadvertisement. If the user is not watching the advertisement, theadvertiser is not receiving the optimal return on their advertisement.

Various innovations with regard to Internet-based advertising haveaddressed some of these concerns. See, for example, U.S. patentapplication Ser. No. 12/617,590, Segment Optimization for TargetedAdvertising and U.S. patent application Ser. No. 12/410,400, PredictingUser Response to Advertisements, each of which is commonly owned by theassignee of this application, and each of which is incorporated hereinin its entirety by this reference thereto.

It has been found that advertiser interaction with the data elements ofthe advertiser's webpage may be helpful for the advertiser. For example,an advertiser may want determine the behavior of the end user byobserving the areas of the website with which the user interacts. Thus,an advertiser may want to add code to the advertiser's webpage tocollect such behavior information. Tag management is a technique thathas been employed to allow adding code to the advertiser's webpage. Tagmanagement is a technique that adds code to an advertiser's webpage byeliminating the need for advertisers to modify code on each individualwebpage and by allowing marketers, as opposed to informationtechnologists of an IT department, to control the content on the webpagethat should be observed. Tag management basically operates by causing awebsite, when opened in a browser, to deploy a generic piece of code,such that when the code executes, data is dynamically collected fromthat website based on predetermined rules.

SUMMARY OF THE INVENTION

A system for creating and using a universal tag to gather consumer datafrom a website and for analyzing the gathered consumer data is provided.An embodiment of the invention provides a universal tag system that hastwo main subsystems. The first subsystem is a configuration system thatis used to define the consumer data to be collected from the website andto define taxonomy and transformation rules to be applied to thecollected consumer data. The second subsystem is a runtime system thatruns a universal tag client-side script, which is triggered when aconsumer lands on a webpage of the website, and that is used forcollecting the defined consumer data. The runtime system then appliesthe transformation rules to the collected data and updates a userprofile of the consumer with the transformed data. As well, the runtimesystem applies the taxonomy rules to the collected data and categorizesthe consumer for the purpose of subsequent targeted advertising.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing components of a configurationsubsystem and a runtime subsystem of a universal tag system according toan embodiment;

FIG. 2 is a schematic diagram of a data schema used by the universal tagsystem according to an embodiment of the invention;

FIG. 3 is a schematic diagram of a universal tag configuration messagesequence for an event definition according to an embodiment of theinvention;

FIG. 4 is a schematic diagram of a universal tag configuration messagesequence for a contract definition according to an embodiment of theinvention;

FIG. 5 is a flow diagram showing the interactions between a window, auniversal tag reporter, presentation server, and a profile server atruntime according to an embodiment of the invention;

FIG. 6 is a schematic diagram showing the communication betweenuniversal tag script components when the script is run according to anembodiment of the invention;

FIG. 7 is a flow diagram showing a particular universal tag endpointinternal message sequence according to an embodiment of the invention;

FIGS. 8A and 8B show a user interface for a universal tag data providerlist page and a flow diagram for creating a universal tag for datacollection according to an embodiment of the invention;

FIG. 9A is a flow diagram for creating a taxonomy hierarchy andassociating an appropriate campaign beacon according to an embodiment ofthe invention;

FIG. 9B is a chart showing an example use case of a user generating aKey/Value pair of the referrer (URL) to capture when the consumer hasbeen to the shopping cart page and generating a taxonomy, which trackshigh and low value carts by defining cart value ranges according to anembodiment of the invention;

FIG. 10 shows a user interface for creating a data provider according toan embodiment of the invention;

FIG. 11 shows details of a user interface for creating a universal tagbookmarklet according to an embodiment of the invention;

FIG. 12 shows a user interface having an installed bookmarklet in thebookmark bar according to an embodiment of the invention;

FIG. 13A shows a user interface having a blank overlay event inspectorpanel that was triggered by the installed bookmarklet according to anembodiment of the invention;

FIG. 13B shows an example event inspector panel for FIG. 13A, which ispopulated with data after the user has logged into the system consoleaccording to an embodiment of the invention;

FIG. 14 shows a user interface having the event inspector overlay thatis populated with configured page elements that may be capturedaccording to an embodiment of the invention;

FIG. 15 shows a user interface having a page tree of user interfaceelements as well as how a user may input events and save according to anembodiment of the invention;

FIG. 16 shows a user interface with which a user may interactivelyselect an element in the page and the overlay panel automaticallyupdates to show which item is selected according to an embodiment of theinvention;

FIG. 17 shows a plurality of panel variations as well as an errormessage box for any panel according to an embodiment of the invention;

FIG. 18 shows a user interface having an example panel according to anembodiment of the invention;

FIG. 19 shows a user interface in which the panel can link back to thedata provider edit page of the console according to an embodiment of theinvention;

FIG. 20 shows a user interface having an error message about an erroroccurring while attempting to retrieve data from the website accordingto an embodiment of the invention;

FIG. 21A shows a user interface in which a user may add an eventmanually according to an embodiment of the invention;

FIG. 21B shows two user interfaces for required type and attribute of anevent added manually according to an embodiment of the invention;

FIG. 22 shows a user interface for creating a new data contractaccording to an embodiment of the invention;

FIG. 23 shows a user interface having a general tab for contractcreation in which a user enters the name, currency, and whichadvertisers according to an embodiment of the invention;

FIG. 24A shows a user interface having a list of previously enteredevents, which the user may browse according to an embodiment of theinvention;

FIG. 24B shows user interfaces with which the user may browse detailedinformation for a particular event, how to make transformations on aparticular key, and how to add text descriptions according to anembodiment of the invention;

FIG. 25A shows a user interface with which new parent nodes and newchild nodes can be set according to an embodiment of the invention;

FIG. 25B shows a user interface for creating node rules and a rule dropdown populated with the same events that are available during theprovider setup flow according to an embodiment of the invention;

FIG. 26A shows a user interface in which a user may import apre-existing taxonomy file according to an embodiment of the invention;

FIG. 26B shows a user interface in which a message is displayed when ataxonomy list is too large to import according to an embodiment of theinvention;

FIG. 27 shows four user interfaces having variations on user-createdgroups by indenting rules according to an embodiment of the invention;

FIG. 28 shows a user interface the provides an example taxonomy andassociated rules according to an embodiment of the invention;

FIG. 29 shows a user interface in which a campaign beacon that isassociated with a particular contract is created according to anembodiment of the invention;

FIG. 30A shows a user interface in which a user may drag and drop ataxonomy node at any parent or child location according to an embodimentof the invention;

FIG. 30B shows a message box with a warning that if the user drops thenode to a parent level, the corresponding rules are lost according to anembodiment of the invention;

FIG. 31 shows user interfaces for building a shopping cart value segmentaccording to an embodiment of the invention;

FIG. 32 shows a user interface for a user to target ads to consumersusing particular segments according to an embodiment of the invention;and

FIG. 33 is a block schematic diagram of a system in the exemplary formof a computer system according to an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

A system for creating and using a universal tag to gather consumer datafrom a website and for analyzing the gathered consumer data is provided.An embodiment of the invention provides a universal tag system that hastwo main subsystems. The first subsystem is a configuration system thatis used to define the consumer data to be collected from the website andto define taxonomy and transformation rules to be applied to thecollected consumer data. The second subsystem is a runtime system thatruns a universal tag client-side script, which is triggered when aconsumer lands on a webpage of the website, and that is used forcollecting the defined consumer data. The runtime system then appliesthe transformation rules to the collected data and updates a userprofile of the consumer with the transformed data. As well, the runtimesystem applies the taxonomy rules to the collected data and categorizesthe consumer for the purpose of subsequent targeted advertising.

Overview

In an embodiment, generic JavaScript code, which may be referred to inthe industry as a pixel of code, is placed on one or more pages of aparticular website and, thereafter, is executed to collect predefineddata from the website when the website pages load. Such code allows auser, e.g. an advertiser, to select and capture particular events thatoccur on the website. For example, user interface events (“events”)occur when a user interacts with the user interface (UI.) Examples of anevent may include, but are not limited to, a user clicking on a mouse,the cursor hovering over a user interface element, the loading of awebpage, changing an input field, and so on. In the embodiment, dataresulting from events are captured, stored, and transformed inreal-time. Then, the stored data are analyzed and used for generatingtargeted segments, also referred to as audience creation. For example, aparticular audience may be created by applying a set of rules againstparticular data caused by particular occurring events on a particularwebsite. The created audience may then be used as target segments for anadvertiser.

As an example, suppose a user clicks on a shopping cart submission on aparticular advertiser's webpage. In the example, the event is the userclicking on the shopping cart submission. Suppose that the shopping cartincluded a mobile device. Thus, in an embodiment, data reflecting that aparticular customer bought the mobile device are gathered and used fortargeted advertising to that particular customer. As another example,the advertiser may want to target customers who purchased mobile devicesbased upon a different, yet related, advertisement.

In an embodiment, a console tool with a user interface is provided to beused in conjunction with the advertiser's website. The console allows auser to generate the code that is placed on the particular website forcapturing particular data. The code is referred to herein as a universaltag.

Consider the example in which a shopping cart for a particular websiteis submitted. Suppose this shopping cart has two products, each with anassociated price value and a total price value for both items. In anembodiment, the universal tag on the website causes a set of configuredrules to be applied against predefined events that cause the total pricevalue to be captured. For example, suppose that the webpage has aJavaScript variable called shopping_cart. In the example, when theshopping cart is submitted and the subsequent page loads, the valueassociated with the shopping cart variable is captured and is found tobe $219. Further in the example, the system determines, based onpredefined taxonomy rules, that the shopping cart value is greater thana threshold, e.g. $150, and that therefore, the category in which thisparticular cart is placed is a high-end category, as opposed to amedium-end or low-end category. Then, upon determining that thiscustomer is in the high-end category, the system, having been previouslyconfigured, further advertises to this customer in a targeted way.

In an embodiment, a user, such as a marketer, logs into the console tobegin configuring the universal tag and rules so that consumer data maybe collected from a website of interest, e.g. an advertiser's website.The user selects a bookmarklet that is provided on the console userinterface, e.g. by clicking or dragging and dropping the bookmarkletonto the bookmark bar of the browser. The bookmarklet containsJavaScript code that is used to select the data to be retrieved; theconsole is used to create the universal tag and to configure the rules.By selecting such bookmarklet, an application essentially is injectedinto the website. Upon the bookmarklet being selected, the applicationdisplays a window, e.g. an overlaying panel that describes the uniqueuser interface elements that reside on the particular webpage of theadvertiser's website. The user may interact with the webpage and withthis panel at the same time to select and interact dynamically with theobjects on the webpage in which they are interested.

In an embodiment, the end user may manually scroll through a list ofobjects, e.g. UI elements, in the panel as well as search for objects.Or, the user may use a mouse to interact with a particular object. Forexample, the user may use the mouse to cause the display cursor to hoverover an object, which causes updates to be presented to the end user.The updates may include historical data which were previously collectedacross all segments from the same demographic, for example. The user mayselect such object as an object of interest.

In an embodiment, the user can build objects as a generic set of objectsof interest from which data can be collected. Such generic set ofobjects resides in one universal tag that the user may then deployacross all of the webpages of interest. Deploying the one universal tagcauses data about such objects to be automatically collected andsubmitted to a repository, such as an ad server, for subsequentpost-processing, such as but not limited to analysis and audiencecreation.

In an embodiment, analytics are applied directly on a website page. Forexample, when a marketer arrives at a particular advertiser's website,the universal tag, which resides at the page, is executed. When theuniversal tag is executed, it allows the marketer to perform analyticson the page with the data that was collected for each of the objectsspecified in the universal tag.

In an embodiment, indicators, e.g. gear icons, may be displayed next toobjects when the user navigates to the webpage to indicate that data arebeing collected for those objects. As well, the indicators may be linkedto historical data about the objects. For example, when an end user usesa mouse to place the display cursor over one of such objects, theembodiment causes the system to present historical data about theobject. In this way, the user can go to the location where that datawere collected. The user does not have to go to a separate summary ordata report to access related data corresponding to a particular object.The data are brought to the user. As an example, a user logs into awebpage, sees the gear icons that indicate what the user hadinstrumented with his universal tag, and mouse-overs a particular gearto get a report about the corresponding object on the webpage.

An embodiment provides site analytics. As an example, suppose a marketercreated a list of products that were being targeted in the advertisingcampaign. The embodiment allows the marketer to color code the productswith respect to various criteria. Thus, for example, the marketer maylearn from the color coded list of products, in combination with thesite analytics that apply the criteria, that “these products drove themost ROI in my advertising campaign, because given the color, I knowthat these products drove high conversion rates.” That is, an embodimentlinks information from the advertiser's site to the results obtained onthe advertising side and thus closes the loop. Analytics provided in anadvertising platform are made available in the console, thus allowingmarketer to extract the analytics and place the analytics where theanalytics are most relevant, i.e. next to the data that drives them.

Ultimately, the marketer may actually create an advertising campaigndynamically from the console using the universal tag and correspondingrules. The user may say, “Here's the data I'm collecting. I see I'vecollected ten million users' worth of data. Now with a single click, Imay go find those users and target them with a campaign.” The process isdriven from the advertiser's site, as opposed to the user having tonavigate to a different application, such as a service's console, toperform such process.

An Exemplary Universal Tag System

Overview

An embodiment can be understood with reference to FIG. 1, a schematicdiagram showing components of a configuration subsystem 102 and aruntime subsystem 104 of a universal tag system 100 (“system.”) In anembodiment, configuration subsystem 102 defines which data a universaltag script should collect and how the data should be used in the adservers, e.g. by allowing rules about the data to be configured. Runtimesubsystem 104 runs the universal tag script, collects the data, andfeeds the data to ad servers for storage and any post-processing.

In an embodiment, components of configuration subsystem 102 comprise butare not limited to a console UI 106, a UI for collecting live data (alsoreferred to herein as Event Inspector) 108, and a runtime code generator110. In an embodiment, components of runtime subsystem 104 comprise butare not limited to a client-side script 114 and a runtime endpoint 112.

Data Model

In an embodiment, a data schema or model is provided as depicted in FIG.2. It should be appreciated that such particular details are for thepurposes of understanding, are by way of example, and are not meant tobe limiting. Examples of data types in the schema includes but are notlimited to TransformationType, Transformation Rule, Taxonomy Category,DataProvider, PageEvent, DataContractKey, etc.

Page Event

In an embodiment, an event is also referred to herein as a page event.Page event definitions determine what data a universal tag script shouldcollect from a advertiser's webpage. These definitions may be manuallyentered via console UI 106 or automatically via the Event Inspector 108.Event inspector 108 may be a widget inside of an advertiser's webpage,such as for example a panel overlaying the webpage, which is describedin further detail hereinbelow.

Universal Tag Data Contract

In an embodiment, a universal tag data contract is created using theconsole in conjunction with the advertiser's website. The data contractis a contract between the advertiser's webpage and one or moreadvertisers. The data contract may specify which of the events on awebpage to capture and how to transform the data from the captured eventfrom an original format to a format for storage. A data contractdefinition may determine how event data that have been collected may beinterpreted for generating user profile data such as key-values andcategorizations. An example of key-value data is a referrer URL as thekey and the URL string as the value. The transformation in this exampleis exact, which means keep the same value as the transformed value. Anexample categorization is high-end. Such interpretation may beaccomplished by applying the defined transformation rules and taxonomyrules of the contract to event data that has been collected.

Configuration System

In an embodiment, configuration system 102 may be a client-facinginterface which may be used by users, such as but not limited tomarketers, to perform the following but is not limited to the following:

-   -   Create the universal tag;    -   Define what data the universal tag may collect at runtime;    -   Define how the collected data may be interpreted by related        systems via transformations; and    -   Define taxonomy rules based on the data that are collected.

In an embodiment, configuration system 102 is comprised of threesubsystems: a console UI 106 to create and manage universal tags; aninjected-script application, live UI 108, also referred to as EventInspector 108, which a user may use to define context-specific datapoints in their live sites; and a listener application on a server(herein referred to as “presentation server”), runtime code generator110, which listens for and converts new data contracts and new eventdefinitions to runtime Java code to update existing Java code.

Console UI

In an embodiment, console UI 106 may be considered a primary entry pointto the workflow of universal tag system 100. Console 106 may beresponsible for the creation and management of the universal tag. A usermay be able to define data points, e.g. events, and be able to view datapoints that have been designated for the tag thus far. The events may beentered manually or via Event Inspector 108. Console 106 may also allowthe user to define data contracts and taxonomy rules using the datapoints that have been defined.

An embodiment is illustrated in FIG. 3, which is a diagram of auniversal tag configuration message sequence for an event definition. Inthis embodiment, a console server 302 receives an instruction to save anevent definition and sends such event definition to be stored at adatabase 304. As well, console server 302 touches a contract at database304, which notifies a presentation server 306 of an update to acontract. Presentation server 306 requests an updated contract fromdatabase 304, which responds, accordingly. Presentation server 306rebuilds the contract and provider runtime objects and sends updatedruntime objects to a presentation server 308. In an embodiment,presentation server 308 pulls data from presentation server 306, ratherthan presentation server 306 pushing the data.

In FIG. 4, a flow diagram of a universal tag configuration messagesequence for a contract definition in accordance with an embodiment isprovided. Console server 302 receives a request to save data aboutcontracts and sends such data to database 304 for storage. Database 304notifies presentation server 306 of the update. Presentation server 306requests the related updated contract from database 304 and receivessuch update. Presentation server 306 generates Java code fromcorresponding transformation and taxonomy rules and sends such generatedruntime objects to presentation server 308. In an embodiment,presentation server 308 pulls data from presentation server 306, ratherthan presentation server 306 pushing the data.

Event Inspector

In an embodiment, a universal tag Event Inspector is an application,which runs in the context of an advertiser's webpage to enable userssuch as but not limited to marketers to define context-specific datacollection points without the need for technical knowledge of thewebpage. Such application may be instantiated on the website by the userclicking an event inspector bookmark on their browser. The applicationmay be responsible for providing the client with a user interface, e.g.an event inspector panel, to explore data on the webpage and todesignate for collection any data that are available to be collected bythe universal tag on the webpage.

In an embodiment, because such application may modify client data froman external origin security concerns may be addressed by, for example,use of a secure top level domain (see FIG. 10; 3.1).

Runtime Java Code Generator

In an embodiment, presentation server 306 listens for new data contractdefinitions or new event definitions. When a new data contract isdetected, the runtime Java code generator on presentation server 306generates the Java code for evaluating the related transformation andtaxonomy rules. Presentation server 306 pushes such generated code topresentation server 308 to be executed at runtime. When a new eventdefinition is detected, the runtime Java code generator may update aruntime provider object and push such object to presentation server 308.

Following are sample new classes and changes to existing classes forillustrative purposes only and are not meant to be limiting.

New Classes:

-   -   RuntimeKVTransform;    -   RuntimeTaxTransform; and    -   RuntimePageEvent        Changes to Existing Classes:    -   RuntimeDataContractCorpus must have a getByProviderId(int);    -   RuntimeDateContract must have List<RuntimeTransformation>;    -   RuntimeDataProvider must have List<RuntimePageEvent>; and    -   SegmentRuleBuilder and SegmentAttributionRuleBuilder must        support new SegmentRule types.        Runtime System

In an embodiment, runtime system 104 may be an automated system which istriggered by universal tag script codes which reside on advertisers'websites. For example, when a website loads, the universal tag scriptcodes may activate runtime system 104. Responsibilities of runtimesystem 104 may include but are not limited to the following. Here,client-defined refers to the user such as the marketer and user refersto the consumer at the website.

-   -   Collect the event data the universal tag is configured to        collect;    -   Apply the client-defined transformation to the collected data        and store such transformation in the user profile of the        consumer; and    -   Apply the client-defined taxonomy rules on the collected data        and categorize users accordingly.

In an embodiment, runtime system 104 may be comprised of two subsystems:a universal tag script 114 and an endpoint 112 with which tag script 114communicates. Endpoint 112 applies the transformation and taxonomy rulesto incoming data.

A runtime message sequence in accordance with an embodiment may beunderstood with reference to FIG. 5, which is a flow diagram showing theinteractions between a window 502 such as the consumer's browser, auniversal tag reporter 504, presentation server 308, and a profileserver 508.

1. A client's user visits a client's website 502 which has the universaltag script embedded in it.

2. A request is made to presentation server 308 to provide the universaltag script for a given provider id.

3. Presentation server 308 gathers the event definitions relevant to thegiven provider id.

-   -   a. The presentation server uses the providerld to retrieve a        List<RuntimeDataContract> from the RuntimeDataContractCorpus;        and    -   b. It also extracts List<RuntimePageEvent> from the        RuntimeDataProvider object (which is retrieved from one of the        RuntimeDataContracts)

4. Presentation server 308 puts the generic universal tag, along withprovider-specific events to collect in the HTTP response body and sendsit back to the client's user's browser 502.

5. The browser 502 interprets the script, creating universal tagreporter 504.

6. For each event definition, the reporter 504 makes API calls to theWindow 502 object to resolve the event expressions.

7. The browser 502 provides evaluated event data to the reporter 504.

8. The reporter 504 posts a key-value list of event names and valuesalong with the providerid and userid to the presentation server 308.

9. The presentation server 308 acknowledges receipt immediately.

10. The presentation server 308 applies transformation and taxonomyrules to the returned keys.

-   -   a. Provider id is used to retrieve relevant RunTimeDataContracts        vis RuntimeDataContractCorpus; and    -   b. For each KVTransform and TaxTransform in all        RuntimeDataContracts, run the transforms, resulting in a map of        key-values and a list of category ids for each contract.

11. Presentation server 308 requests the user profile from a profileserver 508 for the given userid.

12. Profile server 508 responds with the user profile.

13. The user's profile is annotated with the data with transformedkey-values and taxonomy category ids.

14. The annotated profile is pushed back to Profile server 508. Itshould be appreciated that there are two profiles that may be pushed:one for analytics and one for runtime.

Universal Tag Script

In an embodiment, the universal tag script runs in the context of theclient's webpage and is responsible for collecting event data for eventswhich have been defined in configuration system 102 and for reportingsuch event data back to runtime endpoint 112.

An embodiment of universal tag script components and communication canbe understood with reference to FIG. 6. Presentation server 308 requeststo report data to window 502, which sends collected data back topresentation server 308. In the embodiment, window 502 comprises but isnot limited to a universal tag component 602, which communicates withpresentation server through an API component 606 and a reportercomponent 608. As well, universal tag component 602 comprises anexpression evaluator comprising a JavaScript interpreter 612 and a DOMElement Value interpreter 614. JavaScript interpreter 612 communicateswith window API 604 and DOM Element Value interpreter 614 communicateswith DOM API 616.

It should be appreciated that in an embodiment, having the tag script ona clients' website may substantially increase the number of HTTPconnections that are made with presentation server 308. Such increasemay be mitigated through the use of a caching reverse proxy.

Runtime Endpoint

In an embodiment, runtime endpoint 112 runs on presentation server 308and is a communication point for the client-side universal tag script.Universal tag runtime endpoint 112 is responsible for generating theclient-side universal tag script for a given provider id and providingthe list of data collection points from which to retrieve data. Theuniversal tag script may then report the data back to such endpoint 112,where the transformation rules which were defined in the configurationsystem 102 may be applied. The system may then annotate the given user'sprofile with the transformed data and update the profile server 508.

An example implementation in accordance with an embodiment isillustrated in FIG. 7, which is a flow diagram showing a particularuniversal tag endpoint internal message sequence 700. A consumer'sbrowser 702 sends a list of collected events and values and thecorresponding provider id to a data provider servlet application 704.Data provider servlet application 704 sends the provider id to a runtimedata contract corpus 706, which returns a list of corresponding datacontracts. An iterative loop process convenes. Data provider servletapplication 704 sends a request for a list of corresponding runtimetransformations applications from a runtime data contract application708. Data provider servlet application 704 then sends an <event, value>pair to a runtime transform application 710 to perform the appropriatetransformation on the <event, value> pair. Runtime transform application710 returns <key, value> pair and an appropriate category id. Upontermination of the iterative process, data provider servlet application704 sends a user id and the corresponding list of <key, value> pairs andthe user id and the corresponding category id to a runtime user profileapplication 712 for storage.

An Exemplary User Interface and Related Workflows

One or more embodiments of a user interface for a universal tagmanagement tool and related workflows may be understood with referenceto the following figures. It should be appreciated that particulardetails are by way of example and are not meant to be limiting.

FIG. 8A is user interface of a universal tag data provider list page andnavigation page as provided in console UI 106, in accordance with anembodiment. From here, a user may view the list of existing dataproviders or may create a new data provider. As well, the user may viewa list of existing data contracts or create a new data contract.

As well, FIG. 8B shows a high level workflow of the steps the user mayneed to take to create an active universal tag data collection. Itshould be appreciated that particular details are by way of example onlyand are not meant to be limiting.

In Step 1, the user sets up a data provider.

In Step 2, the user selects if the user wants to use a provider withuniversal tag availability.

In Step 3, the user enters allowed domains for universal tag security.

Step 4 is optional and is for the user to enter a name for the processand any notes. Next (step number not listed), the user decides if hewants to use the Event Inspector. If no, he may add event definitionsmanually via the console. If yes, the user proceeds to Step 5.

In Step 5, the user drags and drops the Event Inspector bookmarklet.

In Step 6, the user enters the URL which launches the first page of thewebsite for event capture, e.g. the Home page of the website.

In Step 7, when the webpage loads, the user clicks the bookmarklet.

In Step 8, the Event Inspector panel is displayed.

In Step 9, the user confirms the data provider in the provider tab.

In Step 10, the Event Inspector loads the previously captured events inthe provider tab, if any.

In Step 11, the user can begin adding new events interactively or bysearching.

In Step 12, the user navigates to a new page, e.g. shopping cart.

In Step 13, the user clicks the bookmarklet again and the processrepeats from Step 8. When the user is finished configuring the EventInspector for that particular website, the user may go to Step 6, inwhich he may enter a new URL for a new website and continue with theprocess. When the user is done completing configuration for all websites(no step number), control goes to Step 14.

In Step 14, the user may choose to view his configuration, which, inthis example is in an application referred to as “Audience Suite.”

At Step 15, the data provider configuration page is displayed in theapplication.

At Step 16, the data provider configuration page is refreshed withevents that are captured in the Event Inspector as they are defined.

At Step 17, the user is done and exits the application.

FIG. 9A is a flow diagram of a taxonomy setup workflow in accordancewith an embodiment of the invention. It should be appreciated thatparticular details are by way of example only and are not meant to belimiting.

In Step 902, the user creates a new data contract with a singleadvertiser.

In Step 904, the user chooses to add taxonomy.

In Step 906, the user creates a new taxonomy hierarchy through importingan existing taxonomy file or interactively.

In Step 908, the user creates high nodes and low nodes in the taxonomy.FIG. 9B may be referred to as an example.

In Step 910, the user selects high node and configures events and rules,accordingly.

In Step 912, the user sets an event to shop_cart_value, which wasconfigured during the data provider configuration as part of theuniversal tag.

In Step 914, the user configures a rule to be value >$50.

In Step 916, the user associates a particular advertising signal,referred to herein as a campaign beacon. This step serves the purpose ofpushing back to the signal information reflecting the fact that aconsumer conversion has been made. A key aspect is for the system tohave the information that converting segments can then be targeted orconsidered in further optimization analyses.

In Step 918, the user decides if a new campaign beacon needs to becreated. If no, in Step 920, the user chooses an existing campaignbeacon. If yes, in Step 922, the user creates a new campaign beacon.

In Step 924, the user enters particular settings for the new campaignbeacon.

In Step 926, the user decides if he should select a cart value. If no,the taxonomy process ends. If yes, in Step 928, the user associates theselected cart value with the appropriate event.

FIG. 9B is a sample user story to accompany the taxonomy setup workflowof FIG. 9A in accordance with an embodiment of the invention.

FIG. 10 shows a user interface for creating a data provider inaccordance with an embodiment of the invention. In an embodiment, thecontrols are progressively dynamic 3.0. In cases where a market isavailable, only those markets where universal tags are enabled allow thesecond radio button selection, otherwise the default is on the standardprovider. In an embodiment, an add inline help link for the top leveldomains field is provided 3.1. On a “Next” submit, the form shouldvalidate URLs entered in top level domains 3.2. It is believed that mostof the time the user may enter data correctly, such that the processcontinues to the next step. In the event that the domain is mistyped, amessage is shown.

FIG. 11 shows a user interface for creating a universal tag bookmarkletin accordance with an embodiment of the invention. In an embodiment, theJavaScript text is copied to the clipboard when the user clicks “thiscode” 4.0. Such process to create a bookmark may be done manually or thedrag and drop bookmarklet may be found to be an easier method. In anembodiment, the user may not be able to save the data provider with noevents details 4.1. The button may be disabled. The cancel buttoncancels out of the data provider creation workflow. Back returns to theprevious page where the user enters data provider metadata.

FIG. 12 shows a user interface showing the installed bookmarklet in thebookmark bar in accordance with an embodiment of the invention. Thebookmarklet is shown to have been dragged to the bookmark in this case5.0. Sample JavaScript code is shown.

FIG. 13A shows a user interface showing a blank overlay event inspectorpanel that was triggered by the installed bookmarklet according to anembodiment of the invention. The bookmarklet triggers the sidebaroverlay, which displays the page elements that may be captured 6.0. Thepanel may be wider and support more tabs when necessary, when othergroups are needed, for example. The user may need to be logged in to usethe event inspector 6.1. The panel may link the user to the login page.After login the user should be redirected back to the URL that wasentered. The user may reactivate the bookmarklet, for example.

FIG. 13B is an example event inspector panel for FIG. 13A, which ispopulated with data after the user has logged into the system consoleaccording to an embodiment of the invention.

FIG. 14 shows a user interface showing the event inspector overlay thatis populated with configured page elements that may be captured, inaccordance with an embodiment. The bookmarklet triggers the sidebaroverlay, which displays the page elements that can be captured 7.0. Thepanel may be wider and support more tabs when necessary (when othergroups are needed). The Save button may have a grey/disable state whenthere are no events to save, affording its purpose when it becomesactive, e.g. the user selects something to capture. This gives the userassurance that something is happening, e.g. feedback. When possible thepanel may link back to an audience suite and this data provider's editpage 7.1. The initial tab may be “Provider” 7.2. The provider the userselected in the audience suite may be the default, e.g. in the usualcase of the user starting a new provider in the audience suite, it maybe likely that the correct provider is the last one selected. However,the drop down allows the user to change data providers. Theobjects/events the user previously captured may be shown along with thecurrent name value 7.3. The user should not be able to change this namein this context for v1 or the attribute. Also, when the user choosesanother tab, the previously selected objects may show in the list withthe given name. An embodiment does not “hide” previously configuredobjects. It may be important to optimize the panel for efficiency. Formcapture may be the main use case and, therefore, form capture may bepresented as a primary interface element even when it may technicallythe same as any other HTML element.

FIG. 15 shows a user interface showing a page tree of user interfaceelements as well as how a user may input events and save in accordancewith an embodiment of the invention. The HTML/CSS tab shows the pagetree of UI elements 8.0. This may be separated from the JavaScript treebecause the two tasks may require different levels of understanding.When the user selects an object/event then the form fields dynamicallydisplay allowing the user to name the event with a friendly name and theattribute drop down defaults to a common value (such as “value” forinput fields) 8.1. The user may input many objects/events and then clicksave.

FIG. 16 shows a user interface showing that a user may interactivelyselect an element in the page and the overlay panel automaticallyupdates to show which item is selected in accordance with an embodimentof the invention. For example, the user may interactively selectelements in the page and the HTML panel may update to show which item isselected 9.0. The page listener may only be active in this mode. Thepanel tells the user that he may use the mouse pointer. Because the usermay be pointing to an element on the page that is not the target object,in this mode, the hierarchy may be shown and may be interactivelyclicked 9.1.

FIG. 17 shows a plurality of panel variations as well as an errormessage box for any panel in accordance with an embodiment of theinvention. The user may select any object listed 10.0. The form elementsshould be listed with the type of element and the best identifier. Inthe case of Input elements, Name. The name field is dynamically shown onClick 10.1. The name persists in the field until the user saves orcloses the panel. On close, the warning popup should be shown. Scrollbar scrolls the entire panel 10.2. On first use, the user may likelynotice that there is an HTML and a Forms section. Data are buffered whenthe form elements with event names push the HTML section down the panel.The panel height may be maximized on height given the browserresolution. When the user types into the search field, the contentupdates showing only the objects that match the query (against ID andname) 10.3. An example of the JavaScript is shown 10.4.

FIG. 18 shows a user interface showing an example, refined panel inaccordance with an embodiment of the invention. This UI shows a morerefined look and feel for the panel and should be the guide for thelayout and visual design 11.0. The other panels provided may bewireframes and not pixel perfect.

FIG. 19 shows a user interface showing how the panel can link back tothe data provider edit page of the console in accordance with anembodiment of the invention. The panel links back to the data provideredit page when possible 12.0. The button is disabled unless manualevents are added 12.1. The Event Inspector events that are updateddynamically do not require resaving, unless the user changes the name. Apolling mechanism should check to see if new events are added 12.2. Whenevents are found then a message is shown until the next poll interval.

FIG. 20 shows a user interface showing an error message about an erroroccurring while attempting to retrieve data from the website inaccordance with an embodiment of the invention. The error case showserror a message widget 13.0.

FIG. 21A shows a user interface showing how a user may add an eventmanually in accordance with an embodiment of the invention. When theuser clicks “Add Manual Event” a new line is added to the table at theend with the [x] button to remove it 14.0. The user then selects thetype of captured event 14.1. The other fields dynamically update basedon selection. The user can select form fields, selection by ID (HTMLobjects) or CSS expressions. Each manual entry requires an objectidentifier (the name of the form field, the ID or the CSS expression)and the attribute to capture (value is default for form field, innerHTMLfor div, etc.) As much as possible, intelligent defaults are used. FIG.21B shows two user interfaces for required type and attribute of anevent added manually according to an embodiment of the invention.

FIG. 22 shows a user interface for creating a new data contract inaccordance with an embodiment of the invention. When the user clicks NewData Contract, the same workflow window as in regular Data Contracts isloaded 15.0. The provider is either Universal Tag or not.

FIG. 23 shows a user interface showing the general tab for contractcreation in which a user enters the name, currency, and whichadvertisers in accordance with an embodiment of the invention. Thegeneral tab in the contract creation flow is the same as regular datacontract 16.0. The user may enter name, currency and which advertisers.The user selects single advertiser for many use cases including creationof a conversion event that is used in the campaign suite 16.1.

FIG. 24A shows a user interface showing a list of previously enteredevents, which the user may browse according to an embodiment of theinvention. FIG. 24B shows how, in a user interface, the user may browsedetailed information for a particular event, how to make transformationson a particular key, and how to add text descriptions according to anembodiment of the invention. The user may browse the previously enteredevent list for that particular tab 17.0. The user may maketransformations on the key 17.1. When a selection is made requiring avalue, the form field is dynamically shown. A taxonomy capture control17.2 as a secondary option is provided. 17.3 shows the user is allowedto add a character limited description of the data being captured.

FIG. 25A shows a user interface showing how to set new parent nodes andnew child nodes according to an embodiment of the invention. FIG. 25Bshows a user interface for creating node rules and a rule drop downpopulated with the same events that are available during the providersetup flow according to an embodiment of the invention. The user canquickly make a taxonomy set using the New Parent and New Child controls18.0. When a child node is created, it requires rules and is denoted assuch. When the user creates a new node, a form control is shown toaccept text entry for name. 18.1. On Enter, the name is created. Whenthe user selects a node, the rule set to the right is shown 18.2. Thefirst drop down is populated with the events captured at the providerlevel. The operator can be set to equal by default or no setting. Exporthas been provided to allow users who feel more comfortable editingtaxonomies in Excel to do so with a taxonomy that has been begun online,and also support the “saving” of taxonomy in this manner for futurereference or editing 18.3. The rule drop downs are populated with thesame events that are available in Key-Value and setup during theprovider setup flow 18.4. They should be separated by type.

FIG. 26A shows a user interface showing a user may import a pre-existingtaxonomy file in accordance with an embodiment of the invention. Theuser may import an xls or csv file using the standard import dialog19.0.

FIG. 26B shows a user interface showing a message displayed when ataxonomy list is too large to import 19.1.

FIG. 27 shows four user interfaces showing variations on user-createdgroups by indenting rules in accordance with an embodiment of theinvention. The rules have been separated from the taxonomy so as not toconflate these sometimes complex features. Adding new rules uses Booleanlogic, even though the logic may be off in certain cases (especially ANDcases) 2702. The user can then create a group by indenting, which thenflips the Boolean. The indent button should only be active when there isa possible group (indent disabled with 1 rule or 2 rules, for example).The Boolean should default to OR, so that if the user “pre-creates” 4rules, it initially makes logical sense. If in 2704 the cart value is11.2, both the group rule and the 3rd rule are true, making the 3rd ruleuseless in this state. The user should not be able to “pre indent” rulesor indent rules out of order. There may be interim states that may beillogical without validation 2706. In this case the 1st rule is uselesswhen the cart value is 11.2. However, this again may be an interim stateuntil the user creates a new group by indenting the rule 2708. The addbutton should add a blank rule below the currently clicked rule andwithin that rule's group. The user can then outdent if desired, but thelogic should follow (flipping Boolean.) The delete button removes theselected rule and updates any group logic. If the user deletes one oftwo rules in a group, the group is then lost and the remaining ruleoutdents to the outer rule group, and takes on that rule group Boolean.

FIG. 28 shows a user interface showing example taxonomy and associatedrules in accordance with an embodiment of the invention. For example,one or more shop-cart-value categories can be created 21.0. In the newbeacon example, the advertiser is JCPenney, the beacon type is Sale, thebeacon name is shop_cart_value High, the action type is click and viewthrough, the action cap is unlimited, the protocol is https, and optionsis selected by which the shopping cart total value is passed on to thecampaign beacon.

FIG. 29 shows a user interface showing how a campaign beacon that isassociated with a particular contract is created in accordance with anembodiment of the invention. The user can quickly make a taxonomy setusing the New Parent and New Child controls 22.0. When a child node iscreated, it requires rules and is denoted as such.

FIG. 30A shows a user interface showing how a user may drag and drop ataxonomy node at any parent or child location in accordance with anembodiment of the invention. The user can drag and drop the node usingthe grippy 23.0. The user can drop the node at any parent or childlocation and then tree control should create a temporary branch for thenode. Because the order does not matter in the taxonomy itself, thechild node can be inserted at the end. When the user drops the node to aparent level, the rules are lost 23.1. The console should warn using amodal dialog.

FIG. 30B shows a message box with a warning that if the user drops thenode to a parent level, the corresponding rules are lost according to anembodiment of the invention.

FIG. 31 shows a user interface showing a segment builder in accordancewith an embodiment of the invention. A segment refers to a marketsegment, which is a particular group of consumers defined based oncertain criteria for targeting purposes. For key/value data, the“Sample” link will write the first entry to the field to give the user aclue as to format (error prevention) 24.0. The selection for taxonomydata contracts should match the naming scheme used in the data contractstage 24.1. If it is shown as “Taxonomy” there, then use “Taxonomy” hererather than a different term. When the user selects “Select Categories”for Taxonomy based segments, the tree control is presented with thetaxonomy 24.2. If nodes are selected the mouse-over behavior should showthe description field for each node when implemented.

FIG. 32 shows a user interface for a user to target ads to consumersusing particular market segments in accordance with an embodiment of theinvention. When the user is running a campaign, the shopping cart value,e.g. high, created as a segment in audience may be used to target thoseconsumers, to show appropriate marketing 25.0.

FIG. 33 shows user interfaces for creating a macro for an event forthree different macro types in accordance with an embodiment of theinvention. The types shown for illustrative purposes are DOM Text 3302;DOM Attribute 3304; and JavaScript Variable 3306.

An Example Machine Overview

FIG. 34 is a block schematic diagram of a system in the exemplary formof a computer system 3500 within which a set of instructions for causingthe system to perform any one of the foregoing methodologies may beexecuted. In alternative embodiments, the system may comprise a networkrouter, a network switch, a network bridge, personal digital assistant(PDA), a cellular telephone, a Web appliance or any system capable ofexecuting a sequence of instructions that specify actions to be taken bythat system.

The computer system 3500 includes a processor 3502, a main memory 3504and a static memory 3506, which communicate with each other via a bus3508. The computer system 3500 may further include a display unit 3510,for example, a liquid crystal display (LCD) or a cathode ray tube (CRT).The computer system 3500 also includes an alphanumeric input device3512, for example, a keyboard; a cursor control device 3514, forexample, a mouse; a disk drive unit 3516, a signal generation device3518, for example, a speaker, and a network interface device 3520.

The disk drive unit 3516 includes a machine-readable medium 3524 onwhich is stored a set of executable instructions, i.e. software, 3526embodying any one, or all, of the methodologies described herein below.The software 3526 is also shown to reside, completely or at leastpartially, within the main memory 3504 and/or within the processor 3502.The software 3526 may further be transmitted or received over a network3528, 3530 by means of a network interface device 3520.

In contrast to the system 3500 discussed above, a different embodimentuses logic circuitry instead of computer-executed instructions toimplement processing entities. Depending upon the particularrequirements of the application in the areas of speed, expense, toolingcosts, and the like, this logic may be implemented by constructing anapplication-specific integrated circuit (ASIC) having thousands of tinyintegrated transistors. Such an ASIC may be implemented with CMOS(complementary metal oxide semiconductor), TTL (transistor-transistorlogic), VLSI (very large systems integration), or another suitableconstruction. Other alternatives include a digital signal processingchip (DSP), discrete circuitry (such as resistors, capacitors, diodes,inductors, and transistors), field programmable gate array (FPGA),programmable logic array (PLA), programmable logic device (PLD), and thelike.

It is to be understood that embodiments may be used as or to supportsoftware programs or software modules executed upon some form ofprocessing core (such as the CPU of a computer) or otherwise implementedor realized upon or within a system or computer readable medium. Amachine-readable medium includes any mechanism for storing ortransmitting information in a form readable by a machine, e.g. acomputer. For example, a machine readable medium includes read-onlymemory (ROM); random access memory (RAM); magnetic disk storage media;optical storage media; flash memory devices; electrical, optical,acoustical or other form of propagated signals, for example, carrierwaves, infrared signals, digital signals, etc.; or any other type ofmedia suitable for storing or transmitting information.

Further, it is to be understood that embodiments may include performingoperations and using storage with cloud computing. For the purposes ofdiscussion herein, cloud computing may mean executing algorithms on anynetwork that is accessible by internet-enabled or network-enableddevices, servers, or clients and that do not require complex hardwareconfigurations, e.g. requiring cables and complex softwareconfigurations, e.g. requiring a consultant to install. For example,embodiments may provide one or more cloud computing solutions thatenable users, e.g. users on the go, to obtain advertising analytics oruniversal tag management in accordance with embodiments herein on suchinternet-enabled or other network-enabled devices, servers, or clients.It further should be appreciated that one or more cloud computingembodiments may include providing or obtaining advertising analytics orperforming universal tag management using mobile devices, tablets, andthe like, as such devices are becoming standard consumer devices.

Although the invention is described herein with reference to thepreferred embodiment, one skilled in the art will readily appreciatethat other applications may be substituted for those set forth hereinwithout departing from the spirit and scope of the present invention.Accordingly, the invention should only be limited by the Claims includedbelow.

The invention claimed is:
 1. A system comprising: a universal tagconfiguration subsystem comprising: a console server operable toconfigure universal tags, each universal tag including a data contractdefinition for: specifying data events and corresponding event data tocollect from a designated website accessed by a user at a user device,and specifying client-defined transformation rules and taxonomy rulesfor interpreting the collected event data to generate a user profilecorresponding to the user, the user profile including key-value pairsand categorizations; wherein the data contract definition is stored as acorresponding updated data contract in a database; and a listeningserver operable to: identify the updated data contract in the database,and generate runtime code instructions based on the updated datacontract; and a runtime subsystem comprising: a profile server forstoring the user profile; and a presentation server operable to: receivethe runtime code from the listening server to instantiate a runtimeendpoint, collect, at runtime, event data from the designated website,the event data specified by the data contract definition, apply thetransformations to the collected event data, categorize the transformedevent data based on the applied taxonomy rules, and store thetransformed event data in the corresponding user profile at the profileserver; wherein collecting event data includes providing a universal tagscript, via the presentation server, for running in the context of thedesignated website to instantiate a universal tag to: collect event datafrom the designated website, and report the collected event data to theruntime endpoint for applying the transformation and taxonomy rules; andwherein applying the transformations to the collected event dataincludes performing an iterative loop via the runtime endpoint on thepresentation server, the iterative loop comprising: automaticallydetermining, via a data provider servlet application, a list of runtimetransformation applications corresponding to data contractscorresponding to a particular provider ID; performing, via a runtimetransform application, the appropriate transformations on event-valuepairs; and for each event-value pair, return a key-value pair andappropriate category identification for storage at a runtime userprofile application.
 2. The system of claim 1, wherein the configurationsubsystem is configured to provide: a console user interface (UI) at theconsole server for creating and managing the universal tags, and anevent inspector tool on the listening server for definingcontext-specific data events for collection on a webpage visited by auser device.
 3. The system of claim 2, wherein the event inspectordefines context-specific data events in a format other than HyperTextMarkup Language.
 4. The system of claim 2, wherein data events areautomatically defined at the console server via the event inspectortool.
 5. The system of claim 1, wherein collecting event data furtherincludes: gathering, via the presentation server, the contractdefinitions corresponding to a given provider identification;transmitting the contract definitions to a client device to instantiatethe universal tag, the universal tag including a universal tag reporter,wherein the universal tag reporter resolves event expressions at theclient device and collects the evaluated event data; and receiving, atthe presentation server, the key-value list of event names and valuesalong with provider identification and user identification correspondingto the collected event data.
 6. The system of claim 1, wherein theuniversal tag includes an expression evaluator comprising: a JavScriptinterpreter communicating with a window application program interface(API), and a document object model (DOM) element value interpretercommunicating with a DOM API of the window API.
 7. The system of claim5, wherein storing the transformed event data in the corresponding oneor more user profiles with the transformed event data at the profileserver includes updating the one or more user profiles via the runtimeendpoint.
 8. A method comprising: configuring a data contract definitionof a universal tag via a console server, wherein the data contractdefinition specifies: data events and corresponding event data tocollect from a designated website accessed by a user at a user device,and client-defined transformation rules and taxonomy rules forinterpreting the collected event data to generate a user profilecorresponding to the user, the user profile including key-value pairsand categorizations; storing the data contract definition as acorresponding updated data contract in a database; identifying, via alistening server, the updated data contract in the database; generating,via the listening server, run time code instructions based on theupdated data contract; receiving, at a presentation server, the runtimecode from the listening server to instantiate a runtime endpoint at thepresentation server; collecting, at the presentation server duringruntime, event data from the designated website, the event dataspecified by the data contract definition; applying the transformationsto the collected event data, categorizing the transformed event databased on the applied taxonomy rules, and storing the transformed eventdata in the corresponding user profile at a profile server; whereincollecting event data includes providing a universal tag script, via thepresentation server, for running in the context of the designatedwebsite to instantiate a universal tag to: collect event data from thedesignated website, and report the collected event data to the runtimeendpoint for applying the transformation and taxonomy rules; and whereinapplying the transformations to the collected event data includesperforming an iterative loop via the runtime endpoint on thepresentation server, the iterative loop comprising: automaticallydetermining, via a data provider servlet application, a list of runtimetransformation applications corresponding to data contractscorresponding to a particular provider ID; performing, via a runtimetransform application, the appropriate transformations on event-valuepairs; and for each event-value pair, return a key-value pair andappropriate category identification for storage at a runtime userprofile application.
 9. The method of claim 8, further comprising:generating a console user interface (UI) at the console server forinputting the client-defined transformation rules and taxonomy rules,and generating an event inspector tool on the listening server fordefining context-specific data events for collection on a webpagevisited by a user device.
 10. The method of claim 9, wherein the eventinspector defines context-specific data events in a format other thanHyperText Markup Language.
 11. The method of claim 9, wherein dataevents are automatically defined at the console server via the eventinspector tool.
 12. The method of claim 8, wherein collecting event datafurther includes: gathering, via the presentation server, the contractdefinitions corresponding to a given provider identification;transmitting the contract definitions to a client device to instantiatethe universal tag, the universal tag including a universal tag reporter,wherein the universal tag reporter resolves event expressions at theclient device and collects the evaluated event data; and receiving, atthe presentation server, the key-value list of event names and valuesalong with provider identification and user identification correspondingto the collected event data.
 13. The method of claim 8, wherein theuniversal tag includes an expression evaluator comprising: a JavScriptinterpreter communicating with a window application program interface(API), and a document object model (DOM) element value interpretercommunicating with a DOM API of the window API.
 14. The method of claim12, wherein storing the transformed event data in the corresponding oneor more user profiles with the transformed event data at the profileserver includes updating the one or more user profiles via the runtimeendpoint.
 15. A non-transitory computer readable medium storing one ormore programs configured for execution by a computer, the one or moreprograms comprising instructions for: configuring a data contractdefinition of a universal tag via a console server, wherein the datacontract definition specifies: data events and corresponding event datato collect from a designated website accessed by a user at a userdevice, and client-defined transformation rules and taxonomy rules forinterpreting the collected event data to generate a user profilecorresponding to the user, the user profile including key-value pairsand categorizations; storing the data contract definition as acorresponding updated data contract in a database; identifying, via alistening server, the updated data contract in the database; generating,via the listening server, run time code instructions based on theupdated data contract; receiving, at a presentation server, the runtimecode from the listening server to instantiate a runtime endpoint at thepresentation server; collecting, at the presentation server duringruntime, event data from the designated website, the event dataspecified by the data contract definition; applying the transformationsto the collected event data, categorizing the transformed event databased on the applied taxonomy rules, and storing the transformed eventdata in the corresponding user profile at a profile server; whereincollecting event data includes providing a universal tag script, via thepresentation server, for running in the context of the designated website to instantiate a universal tag to: collect event data from thedesignated website, and report the collected event data to the runtimeendpoint for applying the transformation and taxonomy rules; and whereinapplying the transformations to the collected event data includesperforming an iterative loop via the runtime endpoint on thepresentation server, the iterative loop comprising: automaticallydetermining, via a data provider servlet application, a list of runtimetransformation applications corresponding to data contractscorresponding to a particular provider ID; performing, via a runtimetransform application, the appropriate transformations on event-valuepairs; and for each event-value pair, return a key-value pair andappropriate category identification for storage at a runtime userprofile application.
 16. The non-transitory computer readable medium ofclaim 15, wherein collecting event data includes providing a universaltag script, via the presentation server, for running in the context ofthe designated website to instantiate a universal tag to: collect eventdata from the designated website, and report the collected event data tothe runtime endpoint for applying the transformation and taxonomy rules.